Sequential memory access operations

ABSTRACT

Methods of operating a memory include performing a memory access operation, obtaining an address corresponding to a subsequent memory access operation prior to stopping the memory access operation, stopping the memory access operation, sharing charge between access lines used for the memory access operation and access lines to be used for the subsequent memory access operation, and performing the subsequent memory access operation.

RELATED APPLICATION

This Application is a continuation of U.S. application Ser. No. 15/244,163, “titled “SEQUENTIAL MEMORY ACCESS OPERATIONS,” filed Aug. 23, 2016, (allowed) which is a continuation of U.S. application Ser. No. 14/479,703, titled “SEQUENTIAL MEMORY ACCESS OPERATIONS,” filed Sep. 8, 2014, now U.S. Pat. No. 9,430,417 issued on Aug. 30, 2016 which is commonly assigned and incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to memory and, in particular, in one or more embodiments, the present disclosure relates to sequential memory access operations sharing charges between access lines.

BACKGROUND

Memory devices are typically provided as internal, semiconductor, integrated circuit devices in computers or other electronic devices. There are many different types of memory including random-access memory (RAM), read only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), and flash memory.

Flash memory devices have developed into a popular source of non-volatile memory for a wide range of electronic applications. Flash memory devices typically use a one-transistor memory cell that allows for high memory densities, high reliability, and low power consumption. Changes in threshold voltage of the memory cells, through programming (which is often referred to as writing) of charge storage structures (e.g., floating gates or charge traps) or other physical phenomena (e.g., phase change or polarization), determine the data value of each cell. Common uses for flash memory include personal computers, personal digital assistants (PDAs), digital cameras, digital media players, cellular telephones, solid state drives and removable memory modules, and the uses are growing.

Power consumption is often an important consideration in the design and usage of memory devices. Speed of memory access can be another important consideration in the design and usage of memory devices.

For the reasons stated above, and for other reasons stated below which will become apparent to those skilled in the art upon reading and understanding the present specification, there is a need in the art for alternative methods of operating memory, and apparatus to perform such methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a simplified block diagram of a memory device in communication with a processor as part of an electronic system, according to an embodiment.

FIG. 1B is a schematic of a portion of an array of memory cells as could be used in a memory device of the type described with reference to FIG. 1A.

FIG. 2 is a simplified block diagram of an address register according to an embodiment as could be used in a memory device of the type described with reference to FIG. 1A.

FIG. 3A shows a timing diagram of a conventional sequential memory access.

FIG. 3B shows a timing diagram of a sequential memory access according to an embodiment.

FIG. 4A is a schematic of a portion of an array of memory cells as could be used in a memory device of the type described with reference to FIG. 1A.

FIG. 4B is a schematic of a driver configuration for global access lines as could be used with the portion of the array of memory cells of FIG. 4A.

FIG. 5 is a flowchart of a method of operating a memory according to an embodiment.

FIG. 6 is a flowchart of a portion of the method of operating a memory of FIG. 5 according to a further embodiment.

FIG. 7 is a flowchart of a portion of the methods of operating a memory of FIG. 5 or 6 according to another embodiment.

FIG. 8 is a simplified block diagram of an array of memory cells organized in tiles according to an embodiment as could be used in a memory device of the type described with reference to FIG. 1A.

DETAILED DESCRIPTION

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown, by way of illustration, specific embodiments. In the drawings, like reference numerals describe substantially similar components throughout the several views. Other embodiments may be utilized and structural, logical and electrical changes may be made without departing from the scope of the present disclosure. The following detailed description is, therefore, not to be taken in a limiting sense.

Memory access operations, e.g., program operations (sometimes referred to as write operations), read operations and erase operations generally involve the application of various voltages to the control gate, source, drain and/or channel of memory cells of an array of memory cells (e.g., memory array). Between access operations, these voltages are generally discharged.

Access lines to memory cells often present relatively large capacitances due to extended conductor runs, such that a significant amount of power and time can be expended in bringing these access lines to their desired voltage levels. Various embodiments described herein seek to reduce the power and time requirements necessary to bring access lines to their desired voltage levels by incorporating sharing of charge between access lines used during one memory access operation (e.g., a prior access operation) and access lines used during a subsequent access operation. By sharing charge between access operations, the power and time to bring an access line to its desired voltage level for a particular access operation may be reduced.

FIG. 1A is a simplified block diagram of a first apparatus, in the form of a memory device 100, in communication with a second apparatus, in the form of a processor 130, as part of a third apparatus, in the form of an electronic system, according to an embodiment. Some examples of electronic systems include personal computers, personal digital assistants (PDAs), digital cameras, digital media players, digital recorders, games, appliances, vehicles, wireless devices, cellular telephones and the like. The processor 130, e.g., a controller external to the memory device 100, may be a memory controller or other external host device.

Memory device 100 includes an array of memory cells 104 logically arranged in rows and columns. Memory cells of a logical row are typically coupled to the same access line (commonly referred to as a word line) while memory cells of a logical column are typically selectively coupled to the same data line (commonly referred to as a bit line). A single access line may be associated with more than one logical row of memory cells and a single data line may be associated with more than one logical column. Memory cells (not shown in FIG. 1A) of at least a portion of array of memory cells 104 are capable of being programmed to one of at least two data states.

A row decode circuitry 108 and a column decode circuitry 110 are provided to decode address signals. Address signals are received and decoded to access the array of memory cells 104. Memory device 100 also includes input/output (I/O) control circuitry 112 to manage input of commands, addresses and data to the memory device 100 as well as output of data and status information from the memory device 100. An address register 114 is in communication with I/O control circuitry 112 and row decode circuitry 108 and column decode circuitry 110 to latch the address signals prior to decoding. A command register 124 is in communication with I/O control circuitry 112 and control logic 116 to latch incoming commands.

An internal controller (e.g., control logic 116) controls access to the array of memory cells 104 in response to the commands and generates status information for the external processor 130, i.e., control logic 116 is configured to perform access operations in accordance with embodiments described herein. The control logic 116 is in communication with row decode circuitry 108 and column decode circuitry 110 to control the row decode circuitry 108 and column decode circuitry 110 in response to the addresses.

Control logic 116 is also in communication with a cache register 118. Cache register 118 latches data, either incoming or outgoing, as directed by control logic 116 to temporarily store data while the array of memory cells 104 is busy writing or reading, respectively, other data. During a program operation (e.g., write operation), data is passed from the cache register 118 to data register 120 for transfer to the array of memory cells 104; then new data is latched in the cache register 118 from the I/O control circuitry 112. During a read operation, data is passed from the cache register 118 to the I/O control circuitry 112 for output to the external processor 130; then new data is passed from the data register 120 to the cache register 118. A status register 122 is in communication with I/O control circuitry 112 and control logic 116 to latch the status information for output to the processor 130.

Memory device 100 receives control signals at control logic 116 from processor 130 over a control link 132. The control signals may include at least a chip enable CE#, a command latch enable CLE, an address latch enable ALE, and a write enable WE#. Additional control signals (not shown) may be further received over control link 132 depending upon the nature of the memory device 100. Memory device 100 receives command signals (which represent commands), address signals (which represent addresses), and data signals (which represent data) from processor 130 over a multiplexed input/output (I/O) bus 134 and outputs data to processor 130 over I/O bus 134.

For example, the commands are received over input/output (I/O) pins [7:0] of I/O bus 134 at I/O control circuitry 112 and are written into command register 124. The addresses are received over input/output (I/O) pins [7:0] of bus 134 at I/O control circuitry 112 and are written into address register 114. The data are received over input/output (I/O) pins [7:0] for an 8-bit device or input/output (I/O) pins [15:0] for a 16-bit device at I/O control circuitry 112 and are written into cache register 118. The data are subsequently written into data register 120 for programming the array of memory cells 104. For another embodiment, cache register 118 may be omitted, and the data are written directly into data register 120. Data are also output over input/output (I/O) pins [7:0] for an 8-bit device or input/output (I/O) pins [15:0] for a 16-bit device.

It will be appreciated by those skilled in the art that additional circuitry and signals can be provided, and that the memory device of FIG. 1A has been simplified. It should be recognized that the functionality of the various block components described with reference to FIG. 1A may not necessarily be segregated to distinct components or component portions of an integrated circuit device. For example, a single component or component portion of an integrated circuit device could be adapted to perform the functionality of more than one block component of FIG. 1A. Alternatively, one or more components or component portions of an integrated circuit device could be combined to perform the functionality of a single block component of FIG. 1A.

Additionally, while specific I/O pins are described in accordance with popular conventions for receipt and output of the various signals, it is noted that other combinations or numbers of I/O pins may be used in the various embodiments.

FIG. 1B is a schematic of a NAND memory array 200, e.g., as a portion of array of memory cells 104. Memory array 200 includes access lines, such as word lines 202 ₀ to 202 _(N), and data lines, such as bit lines 204 ₀ to 204 _(M). The word lines 202 may be coupled to global access lines (e.g., global word lines), not shown in FIG. 1B, in a many-to-one relationship. For some embodiments, memory array 200 may be formed over a semiconductor that, for example, may be conductively doped to have a conductivity type, such as a p-type conductivity, e.g., to form a p-well, or an n-type conductivity, e.g., to form an n-well.

Memory array 200 might be arranged in rows (each corresponding to a word line 202) and columns (each corresponding to a bit line 204). Each column may include a string of series-coupled memory cells, such as one of NAND strings 206 ₀ to 206 _(M). Each NAND string 206 might be coupled to a common source 216 and might include memory cells 208 ₀ to 208 _(N). The memory cells 208 represent non-volatile memory cells for storage of data. The memory cells 208 of each NAND string 206 might be connected in series between a select transistor 210 (e.g., a field-effect transistor), such as one of the select transistors 210 ₀ to 210 _(M) (e.g., that may be source select transistors, commonly referred to as select gate source), and a select transistor 212 (e.g., a field-effect transistor), such as one of the select transistors 212 ₀ to 212 _(M) (e.g., that may be drain select transistors, commonly referred to as select gate drain). Select transistors 210 ₀ to 210 _(M) might be commonly coupled to a select line 214, such as a source select line, and select transistors 212 ₀ to 212 _(M) might be commonly coupled to a select line 215, such as a drain select line.

A source of each select transistor 210 might be connected to common source 216. The drain of each select transistor 210 might be connected to a memory cell 208 ₀ of the corresponding NAND string 206. For example, the drain of select transistor 210 ₀ might be connected to memory cell 208 ₀ of the corresponding NAND string 206 ₀. Therefore, each select transistor 210 might be configured to selectively couple a corresponding NAND string 206 to common source 216. A control gate of each select transistor 210 might be connected to select line 214.

The drain of each select transistor 212 might be connected to the bit line 204 for the corresponding NAND string 206. For example, the drain of select transistor 212 ₀ might be connected to the bit line 204 ₀ for the corresponding NAND string 206 ₀. The source of each select transistor 212 might be connected to a memory cell 208 _(N) of the corresponding NAND string 206. For example, the source of select transistor 212 ₀ might be connected to memory cell 208 _(N) of the corresponding NAND string 206 ₀. Therefore, each select transistor 212 might be configured to selectively couple a corresponding NAND string 206 to a corresponding bit line 204. A control gate of each select transistor 212 might be connected to select line 215.

The memory array in FIG. 1B might be a quasi-two-dimensional memory array and might have a generally planar structure, e.g., where the common source 216, strings 206 and bit lines 204 extend in substantially parallel planes. Alternatively, the memory array in FIG. 1B might be a three-dimensional memory array, e.g., where strings 206 may extend substantially perpendicular to a plane containing the common source 216 and to a plane containing the bit lines 204 that may be substantially parallel to the plane containing the common source 216.

Typical construction of memory cells 208 includes a data-storage structure 234 (e.g., a floating gate, charge trap, etc.) that can determine a data value of the cell (e.g., through changes in threshold voltage), and a control gate 236, as shown in FIG. 1B. In some cases, memory cells 208 may further have a defined source 230 and a defined drain 232. Memory cells 208 have their control gates 236 coupled to (and in some cases form) a word line 202.

A column of the memory cells 208 is a NAND string 206 or a plurality of NAND strings 206 coupled to a given bit line 204. A row of the memory cells 208 are memory cells 208 commonly coupled to a given word line 202. A row of memory cells 208 can, but need not include all memory cells 208 commonly coupled to a given word line 202. Rows of memory cells 208 may often be divided into one or more groups of physical pages of memory cells 208, and physical pages of memory cells 208 often include every other memory cell 208 commonly coupled to a given word line 202. For example, memory cells 208 commonly coupled to word line 202 _(N) and selectively coupled to even bit lines 204 (e.g., bit lines 204 ₀, 204 ₂, 204 ₄, etc.) may be one physical page of memory cells 208 (e.g., even memory cells) while memory cells 208 commonly coupled to word line 202 _(N) and selectively coupled to odd bit lines 204 (e.g., bit lines 204 ₁, 204 ₃, 204 ₅, etc.) may be another physical page of memory cells 208 (e.g., odd memory cells). Although bit lines 204 ₃-204 ₅ are not expressly depicted in FIG. 1B, it is apparent from the figure that the bit lines 204 of the array of memory cells 200 may be numbered consecutively from bit line 204 ₀ to bit line 204 _(M). Other groupings of memory cells 208 commonly coupled to a given word line 202 may also define a physical page of memory cells 208. For certain memory devices, all memory cells commonly coupled to a given word line might be deemed a physical page. The portion of a physical page (which, in some embodiments, could still be the entire row) that is read during a single read operation or programmed during a program operation (e.g., an upper or lower page memory cells) might be deemed a logical page.

Although the example of FIG. 1B is discussed in conjunction with NAND flash, the embodiments described herein are not limited to a particular array architecture or structure, and can include other structures (e.g., cross-point memory, DRAM, etc.) and other architectures (e.g., AND arrays, NOR arrays, etc.).

FIG. 2 is a simplified block diagram of an address register 114 according to an embodiment as could be used in a memory device of the type described with reference to FIG. 1A. In order to share charge between access lines of sequential memory access operations, the memory may need to have access to addresses corresponding to memory access operations. For example, memory access operations are associated with addresses defining where in a memory array, or group of memory arrays, the access operation is to be performed. For example, a program operation may have an associated address identifying one or more memory cells selected for programming. In response to this address, the controller (e.g., control logic 116) can determine what voltages are applied to various access lines to effect that programming. In a NAND architecture memory device containing strings of memory cells, this may involve applying a program voltage to an access line coupled to a selected memory cell of a particular string of memory cells, and applying varying voltages to access lines coupled to other (e.g., unselected) memory cells of the particular string of memory cells. It is recognized that an access line coupled to a selected memory cell for a particular access operation is typically coupled to a large number of other memory cells that may or may not be selected for that particular access operation.

By having access to addresses corresponding to sequential memory access operations, the controller can determine which access lines to select for charge sharing. The address register 114 of FIG. 2 may thus include storage for an address corresponding to a particular memory access operation (e.g., a current or prior memory access operation), such as primary address register 242, and storage for an address corresponding to a subsequent memory access operation (e.g., an immediately subsequent memory access operation), such as secondary address register 244. Addresses may be received in conjunction with each of the sequential memory access operations. Alternatively, subsequent addresses may be generated by the controller, such as where a command defines a series of sequential memory access operations beginning at some starting address, and the controller determines a subsequent address in response to the starting address. Address register 114 may have additional registers (not shown) similar to the primary address register 242 and secondary address register 244.

In the configuration of the address register 114, the controller (e.g., control logic 116) may control a current memory access operation in response to the address information (e.g., address) stored in the primary address register 242, and may control charge sharing operations occurring between the current memory access operation and the subsequent memory access operation in response to the address information stored in the primary address register 242 and the secondary address register 244. Subsequent to any charge sharing operations, the address information from the secondary address register 244 may be transferred to the primary address register 242, providing the controller with the appropriate address for controlling the subsequent memory access operation. The secondary address register 244 is then available to receive address information for a next subsequent memory access operation.

FIG. 3A shows a timing diagram of a conventional sequential memory access. FIG. 3A conceptually depicts that a memory in a conventional memory access may indicate that it is busy, e.g., unavailable to perform other operations, during a memory access operation, e.g., memory access operation Op0 or Op1. In a typical process, at time t0, when the first memory access operation Op0 begins, the memory would indicate that it is busy by transitioning the ready-busy signal RB# to a logic low level. At time t1, when the first memory access operation Op0 is complete, the ready-busy signal RB# is transitioned to a logic high level indicating that it is available for subsequent access. A controller (e.g., external processer 130) might then request data for a subsequent memory access operation Op1. The memory might then indicate that it is busy at time t2 at the start of the memory access operation Op1, and release this indication at the completion of the memory access operation Op1 at time t3.

FIG. 3B shows a timing diagram of a sequential memory access according to an embodiment. FIG. 3B conceptually depicts that a memory in a memory access of various embodiments may continue to indicate that it is busy between sequential memory access operations Op0 and Op1, such as when charge sharing is occurring as described subsequently in more detail. During memory access operation Op0, the address information for the subsequent memory access operation Op1 is obtained, e.g., either received from an external controller (e.g., external processor 130) or generated by an internal controller (e.g., control logic 116), prior to the completion of the memory access operation Op0 at time t1. Because of the charge sharing occurring between times t1 and t2 of FIG. 3B, the subsequent memory access operation Op1 may need less time to precharge its access lines, such that the length of memory access operation Op1, e.g., the length of time between time t2 and time t3, may be reduced in comparison to the convention process of FIG. 3A.

Various embodiments facilitate charge sharing between local access lines (e.g., those coupled directly to strings 206) through a common connectivity to a global access line. FIG. 4A is a schematic of a portion of an array of memory cells as could be used in a memory device of the type described with reference to FIG. 1A and depicting this many-to-one relationship between local access lines (e.g., word lines 202) and global access lines (e.g., global word lines 402).

As depicted in FIG. 4A, a plurality of memory blocks 458 may have their local access lines (e.g., word lines 202) commonly selectively connected to a plurality of global access lines (e.g., global word lines 402). A memory block 458 may include a plurality of memory strings 206 commonly coupled to a particular set of word lines 202. For example, the memory strings 206 ₀-206 _(M) of FIG. 1B, or some portion thereof, may represent a memory block 458. Although FIG. 4A depicts only memory blocks 458 ₀ and 458 ₁ (Block 0 and Block 1), additional memory blocks 458 may have their word lines 202 commonly connected to global word lines 402 in a like manner. Similarly, although FIG. 4A depicts only four word lines 202, memory blocks 458 may include fewer or more word lines 202.

To facilitate memory access operations to specific memory blocks 458 commonly coupled to a given set of global word lines 402, each memory block 458 may have a corresponding set of block select transistors 454 in a one-to-one relationship with their word lines 202. Control gates of the set of block select transistors 454 for a given memory block 458 may have their control gates commonly coupled to a corresponding block select line 456. For example, for memory block 458 ₀, word line 202 ₀₀ may be selectively connected to global word line 402 ₀ through block select transistor 454 ₀₀, word line 202 ₀₁ may be selectively connected to global word line 402 ₁ through block select transistor 454 ₀₁, word line 202 ₀₂ may be selectively connected to global word line 402 ₂ through block select transistor 454 ₀₂, and word line 202 ₀₃ may be selectively connected to global word line 402 ₃ through block select transistor 454 ₀₃, while block select transistors 454 ₀₀-454 ₀₃ are responsive to a control signal received on block select line 456 ₀. For such a configuration, each word line 202 of memory block 458 ₀ (e.g., word line 202 ₀₀) can be commonly connected to its corresponding word line 202 of memory block 458 ₁ (e.g., word line 202 ₁₀) through concurrent activation of their respective block select transistors 454 (e.g., block select transistors 454 ₀₀ and 454 ₁₀), such as concurrently applying a logic high signal to their respective block select lines (e.g., block select lines 456 ₀ and 456 ₁), thereby commonly connecting them to their respective global word line (e.g., global word line 402 ₀). As used herein, a first act and a second act occur concurrently when the first act occurs simultaneously with the second act for at least a portion of a duration of the second act, e.g., block select line 456 ₀ and block select line 456 ₁ are simultaneously at a logic high level for at least a portion of a duration of applying the logic high signal to block select line 456 ₁.

Global access lines are typically coupled to driver circuitry to apply the various voltage levels to the global access lines for the various access operations. To share charge between local access lines, it may be desirable to isolate the global access lines from their respective driver circuitry or otherwise electrically float them. FIG. 4B is a schematic of a driver configuration for global access lines as could be used with the portion of the array of memory cells of FIG. 4A. FIG. 4B shows that global access lines (e.g., global word lines 402 ₀-402 ₃) may be selectively coupled to global access line drivers (e.g., global word line drivers 452 ₀-452 ₃) through driver select transistors 460 ₀-460 ₃, respectively. Although driver select transistors 460 ₀-460 ₃ are shown to be commonly coupled to a single driver select line 462, such that all global word lines 402 ₀-402 ₃ are either commonly connected to, or commonly isolated from, their respective global word line driver 452 ₀-452 ₃, each driver select transistor 460 could receive its own control signal to allow individual connection or isolation.

FIG. 5 is a flowchart of a method of operating a memory according to an embodiment. At 570, an address corresponding to a memory access operation is obtained. For example, an address may be received from an external device, or an address may be determined by an internal controller. The memory access operation is performed at 572. At 574, an address corresponding to a subsequent memory access operation is obtained prior to stopping the memory access operation. For example, the address for the subsequent memory access operation may be obtained by receiving it from an external device while performing the memory access operation, or it may be determined by an internal controller. As noted previously, the address for the memory access operation and the address for the subsequent memory access operation define what access lines are used for each memory access operation. After stopping the memory access operation at 576, charge is shared at 578 between access lines used for the memory access operation and access lines to be used for the subsequent memory access operation. The subsequent memory access operation is then performed at 580.

Stopping the memory access operation may include either suspending the memory access operation (e.g., program suspend) or completing the memory access operation. For a memory access operation that is suspended prior to completion, it might be resumed as a next subsequent memory access operation, and may include sharing charge with an immediately prior memory access operation before being resumed. For such an embodiment, the address corresponding to the memory access operation may be saved, e.g., to an additional register of the address register 114 or other storage of the memory, and then reloaded into the primary address register 242 when the memory access operation is ready to resume. Furthermore, where a memory access operation is suspended, it may be desirable not to discharge the access lines used for that memory access operation after sharing charge with access lines to be used for the subsequent memory access operation.

It may not be advantageous to share charge between some memory access operations, e.g., if sharing of charge would increase the access time and/or increase the power draw of the subsequent memory access operation. As such, certain embodiments may incorporate a decision process to determine if it is desired to share charge between the two memory access operations, e.g., the memory access operation of 572 and the subsequent memory access operation of 580. Criteria for this determination will depend upon the various memory access operations that a memory may be configured to perform. However, selection of these criteria would follow the general guidance that two memory access operations are candidates for sharing charge where a decrease in access time and/or a decrease in power draw of the subsequent memory access operation could be obtained by sharing charge, depending upon the goals (e.g., reduced access time or reduced power draw) of the designer or user. FIG. 6 is a flowchart of a portion of the method of operating a memory of FIG. 5 according to a further embodiment providing for such a decision process. The portion of FIG. 6 may be positioned in place of 578 of FIG. 5.

At 684, a determination is made whether sharing charge between the access lines used for the memory access operation and the access lines to be used for the subsequent memory access operation is desired. If the determination is not to share charge, the access lines used for the memory access operation might be discharged at 686 as in a conventional memory access operation after completion. If charge is desired to be shared, the process continues to 578, where charge is shared between the access lines used for the memory access operation and the access lines to be used for the subsequent memory access operation. After sharing charge, the process might then proceed to 686, where the access lines used for the memory access operation might be discharged.

FIG. 7 is a flowchart of a portion of the methods of operating a memory of FIG. 5 or 6 according to another embodiment. The portion of FIG. 7 provides details of the charge sharing 578 according to an embodiment. At 790, the access lines used for the memory access operation are connected with their corresponding access lines to be used to the subsequent memory access operation. At 792, charge is shared between the connected corresponding access lines. And at 794, the access lines used for the memory access operation are disconnected from their corresponding access lines to be used to the subsequent memory access operation.

Although the methods of FIGS. 5-7 are generally depicted as an ordered series of steps, there is no requirement that all of these steps be performed in the order depicted. For example, the address for the memory access operation and the address for the subsequent memory access operation might both be obtained prior to performing the memory access operation, discharging the access lines used for the memory access operation might occur during or after performing the subsequent memory access operation, and comparing the subsequent memory access operation with the memory access operation, and determining whether to share charge, might occur prior to stopping the memory access operation.

An example of the methods of FIGS. 5-7 will be discussed with reference to Table 1 and FIGS. 4A-4B. Table 1 lists voltage levels that might be applied to various nodes of FIGS. 4A-4B during a program operation (e.g., as the memory access operation), during a read operation (e.g., as the subsequent memory access operation) and during charge sharing. For the example, a memory cell coupled to word line 202 ₀₀ of memory block 458 ₀ is selected for programming during the program operation, and a memory cell coupled to word line 202 ₁₃ of memory block 458 ₁ is selected for reading during the read operation. Further for the example, time t0 is presumed to be the beginning of the program operation, time t1 is presumed to be the completion of the program operation, time t2 is presumed to be the beginning of the charge sharing, time t3 is presumed to be the completion of the charge sharing, time t4 is presumed to be the beginning of discharging the access lines used for the program operation, and time t5 is presumed to be the beginning of the read operation. Note that the example is intended only to illustrate methods described herein. While the example is believed to be representative, the voltage responses of charge sharing listed in Table 1 are assumed and do not represent measured values from any physical device.

TABLE 1 Node Time t0 Time t1 Time t2 Time t3 Time t4 Time t5 402₀ 20 V 10 V 7 V 7 V 0 V 8 V 402₁-402₂ 10 V 10 V 7 V 7 V 0 V 8 V 402₃ 10 V 10 V 7 V 7 V 0 V 3 V 456₀ 25 V 25 V 10 V  10 V  10 V  0 V 202₀₀ 20 V 10 V 7 V 7 V 0 V 0 V 202₀₁-202₀₃ 10 V 10 V 7 V 7 V 0 V 0 V 456₁  0 V  0 V 10 V  0 V 0 V 10 V  202₁₀-202₁₂  0 V  0 V 7 V 7 V 7 V 8 V 202₁₃  0 V  0 V 7 V 7 V 7 V 3 V

In the example of Table 1, at time t0, global word line 402 ₀ is driven to 20V and the block select line 456 ₀ is driven to 25V to activate the block select transistors 454 ₀₀-454 ₀₃ to apply the program voltage of 20V to the selected word line 202 ₀₀ of the program operation. Global word lines 402 ₁-402 ₃ are driven to 10V to apply the inhibit voltage of 10V to the unselected word lines 202 ₀₁-202 ₀₃. The block select line 456 ₁ is driven to 0V (e.g., grounded) to deactivate the block select transistors 454 ₁₀-454 ₁₃, keeping word lines 202 ₁₀-202 ₁₃ at their discharged voltages of 0V.

At time t1, the global word line 402 ₀ is reduced to 10V at the completion of the program operation, resulting in pulling the selected word 202 ₀₀ to 10V. While not necessary, the selected word line 202 ₀₀ for the program operation may be pulled down from its program voltage in order to protect memory cells coupled to word line 202 ₁₀ from accidental program disturb should they be exposed to voltages above the inhibit voltage upon charge sharing.

At time t2, the global word lines 402 ₀-402 ₃ are isolated from the driver circuitry or otherwise allowed to float, and the block select line 456 ₁ is driven to 10V. This activates the block select transistors 454 ₁₀-454 ₁₃, commonly connecting the word lines 202 ₀₀-202 ₀₃ to their corresponding word lines 202 ₁₀-202 ₁₃ in a one-to-one relationship, allowing charge sharing between them through the global word lines 402 ₀-402 ₃. There is an expected voltage drop upon sharing charge from the word lines 202 ₀₀-202 ₀₃, and global word lines 402 ₀-402 ₃, as the word lines 202 ₁₀-202 ₁₃ are starting from a lower voltage level, e.g., 0V. As such, once charge is shared, these lines may equilibrate at around 7V for this example. The actual change in voltage level upon charge sharing will depend upon the starting voltage levels and the structure of the various lines sharing charge.

At time t3, the block select line 456 ₁ is driven to 0V to deactivate the block select transistors 454 ₁₀-454 ₁₃, thereby disconnecting the word lines 202 ₁₀-202 ₁₃ from their corresponding word lines 202 ₀₀-202 ₀₃. At time t4, the global word lines 402 ₀-402 ₃ are driven to 0V (e.g., grounded) to discharge the word lines 202 ₀₀-202 ₀₃. At time t5, the global word lines 402 ₀-402 ₂ are driven to 8V and the block select line 456 ₁ is driven to 10V to activate the block select transistors 454 ₁₀-454 ₁₃ to apply the pass voltage of 8V to the unselected word lines 202 ₁₀-202 ₁₂ of the read operation. Global word line 402 ₃ is driven to 3V to apply the read voltage of 3V to the selected word line 202 ₁₃ to begin the read operation.

In the foregoing example, power savings may be facilitated for the subsequent memory access operation (e.g., the read operation) as word lines 202 ₁₀-202 ₁₂ only need to be raised a fraction of the difference between their discharged voltage level and their desired voltage level, e.g., from 7V to 8V instead of 0V to 8V. This may also facilitate a corresponding time savings. In addition, word line 202 ₁₃ is already above its desired voltage level after the charge sharing at time t4, which can also facilitate power savings as no current is required from its associated driver circuitry to reach its desired voltage.

FIG. 8 is a simplified block diagram of an array of memory cells 804 organized in tiles 805 according to an embodiment as could be used in a memory device of the type described with reference to FIG. 1A. The array of memory cells 804 is depicted to include four tiles 805 ₀-805 ₃. Each tile 805 may include one or more memory blocks, such as memory blocks 458 of FIG. 4A. The memory blocks of the tiles 805 ₀-805 ₃ have their access lines commonly selectively connected to corresponding global access lines. For example, memory strings 206 ₀-206 _(X) (X being some integer value between 0 and M, e.g., {M−1}/2 when M is an odd integer value) of FIG. 1B may represent a memory block of tile 805 ₀, and memory strings 206 _(X+1)-206 _(M) of FIG. 1B may represent a memory block of tile 805 ₂. Similarly, memory strings 206 ₀-206 _(X) of FIG. 1B may represent a memory block of tile 805 ₁, and memory strings 206 _(X+1)-206 _(M) of FIG. 1B may represent a memory block of tile 805 ₃. In addition, memory block 458 ₀ of FIG. 4A may represent a memory block of tile 805 ₀ and memory block 458 ₁ of FIG. 4A may represent a memory block of tile 805 ₁. In this manner, methods of charge sharing of various embodiments can be used in an architecture such as this.

The array architecture described with reference to FIG. 8 may include sequential access from each of the tiles 805. For example, a read command may indicate a desire to read on or more units of 16 KB of data from the array of memory cells 804. The read command may have a starting address corresponding to a 4 KB page of data from tile 805 ₀. In response to the read command, a first read operation may read 4 KB of data D0 from tile 805 ₀ using the starting address, a second read operation may then read 4 KB of data D1 from tile 805 ₁ using a second address determined from the starting address, a third read operation may then read 4 KB of data D2 from tile 805 ₂ using a third address determined from the second address, and a fourth read operation may then read 4 KB of data D3 from tile 805 ₃ using a fourth address determined from the third address. Each address for access of the array of memory cells 804 might be represented by some number of bits, where two of those bits (e.g., two least significant bits) are utilized to indicate to which tile 805 the memory access operation is intended. In such a scheme, each subsequent address could be determined simply by toggling through the combinations of those bits, e.g., 00, 01, 10 and 11, without changing remaining bits of the address. Charge sharing could be utilized between each pair of memory access operations of the sequential memory access.

CONCLUSION

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement that is calculated to achieve the same purpose may be substituted for the specific embodiments shown. Many adaptations of the embodiments will be apparent to those of ordinary skill in the art. Accordingly, this application is intended to cover any adaptations or variations of the embodiments. 

1. (canceled)
 2. A method of operating a memory, comprising: performing a memory access operation; obtaining an address corresponding to a subsequent memory access operation prior to stopping the memory access operation; stopping the memory access operation; sharing charge between access lines used for the memory access operation and access lines to be used for the subsequent memory access operation; and performing the subsequent memory access operation; wherein the memory access operation is a first type of memory access operation, and the subsequent memory access operation is a second type of memory access operation different than the first type of memory access operation.
 3. The method of claim 2, wherein obtaining the address corresponding to the subsequent memory access operation comprises receiving the address from an external controller of the memory.
 4. The method of claim 2, wherein the first type of memory access operation and the second type of memory access operation are each selected from a group consisting of a program operation, a read operation and an erase operation.
 5. The method of claim 2, wherein stopping the memory access operation comprises completing the memory access operation or suspending the memory access operation.
 6. The method of claim 2, further comprising: obtaining an address corresponding to a next subsequent memory access operation prior to stopping the subsequent memory access operation; stopping the subsequent memory access operation; sharing charge between access lines used for the subsequent memory access operation and access lines to be used for the next subsequent memory access operation; and performing the next subsequent memory access operation.
 7. The method of claim 6, wherein stopping the memory access operation comprises suspending the memory access operation, and wherein performing the next subsequent memory access operation comprises resuming the memory access operation.
 8. The method of claim 6, further comprising discharging the access lines used for the memory access operation after sharing charge with the access lines to be used for the subsequent memory access operation.
 9. The method of claim 6, wherein the access lines used for the memory access operation are not discharged after sharing charge with the access lines to be used for the subsequent memory access operation.
 10. A method of operating a memory, comprising: obtaining an address corresponding to a memory access operation; performing the memory access operation; obtaining an address corresponding to a subsequent memory access operation, wherein the address corresponding to the subsequent memory access operation is obtained from a device external to the memory, and obtained while performing the memory access operation; stopping the memory access operation; sharing charge between access lines used for the memory access operation and access lines to be used for the subsequent memory access operation; and performing the subsequent memory access operation.
 11. The method of claim 10, further comprising: indicating that the memory is busy while performing the memory access operation; and continuing to indicate that the memory is busy from a time of stopping the memory access operation to a time of performing the subsequent memory access operation.
 12. The method of claim 10, wherein the memory access operation and the subsequent memory access operation are each of a type selected from the group consisting of a program operation, a read operation and an erase operation, and wherein the memory access operation and the subsequent memory access operation of the same type.
 13. The method of claim 10, wherein stopping the memory access operation comprises completing the memory access operation or suspending the memory access operation.
 14. The method of claim 10, further comprising: obtaining an address corresponding to a next subsequent memory access operation prior to stopping the subsequent memory access operation; stopping the subsequent memory access operation; and performing the next subsequent memory access operation.
 15. The method of claim 14, wherein stopping the memory access operation comprises suspending the memory access operation and wherein performing the next subsequent memory access operation comprises resuming the memory access operation.
 16. The method of claim 14, wherein the access lines used for the memory access operation are not discharged between sharing charge with the access lines to be used for the subsequent memory access operation and resuming the memory access operation.
 17. The method of claim 14, further comprising: prior to performing the next subsequent memory access operation, sharing charge between the access lines used for the subsequent memory access operation and access lines to be used for the next subsequent memory access operation.
 18. A method of operating a memory, comprising: obtaining an address corresponding to a memory access operation; storing the address corresponding to the memory access operation to a first storage of the memory; performing the memory access operation; obtaining an address corresponding to a subsequent memory access operation; storing the address corresponding to the subsequent memory access operation to a second storage of the memory; suspending the memory access operation and storing the address corresponding to the memory access operation to a third storage of the memory; sharing charge between access lines used for the memory access operation and access lines to be used for the subsequent memory access operation; transferring the address corresponding to the subsequent memory access operation to the first storage of the memory; performing the subsequent memory access operation; stopping the subsequent memory access operation; sharing charge between access lines used for the subsequent memory access operation and access lines to be used for resuming the memory access operation; transferring the address corresponding to the memory access operation to the first storage of the memory; and resuming the memory access operation.
 19. The method of claim 18, wherein obtaining the address corresponding to the memory access operation comprises determining that address by an internal controller of the memory from an address corresponding to a prior memory access operation.
 20. The method of claim 18, wherein storing the address corresponding to the memory access operation to the first storage of the memory comprises storing the address corresponding to the memory access operation to a primary register of an address register of the memory, wherein storing the address corresponding to the subsequent memory access operation to the second storage of the memory comprises storing the address corresponding to the subsequent memory access operation to a secondary register of the address register, and wherein storing the address corresponding to the memory access operation to the third storage of the memory comprises storing the address corresponding to the memory access operation to an additional register of the address register.
 21. The method of claim 18, wherein sharing charge between the access lines used for the subsequent memory access operation and the access lines to be used for resuming the memory access operation comprises sharing that charge without discharging the access lines used for the memory access operation after sharing charge between the access lines used for the memory access operation and the access lines to be used for the subsequent memory access operation. 